Skip to content

Safe support for minting a Hypercert #483

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed

Conversation

pheuberger
Copy link
Member

We first need to merge the Hypercerts SDK PR hypercerts-org/hypercerts-sdk#37 and then reference the newly published version here.

Until then this is kept in draft mode.

pheuberger and others added 14 commits February 27, 2025 13:44
With the outstanding renaming of main -> release and dev -> main this
workflow will create a pull request every time a PR is merged into main,
our then main development branch.

I tested this workflow from a temporary branch called release-test. See
an example PR that was created by this workflow here:

  hypercerts-org#478
On every PR against dev, main and release we want to run the following
checks:

* build the frontend w/o errors
* run unit tests
* run linter
The test was erroneously testing for the returning RPC URL to contain
glif.io which was not the case. Since this provider is not specifically
about Glif, it was renamed to FVMProvider.
Change layout place of time and work scopes on the hypercert detail page
…rganize-time-or-work-and-scopes

feat: reorganize time or work and scopes
The TODOs were actually part of a WIP commit, but were not thrown out as
intended after finishing the implementation.
Since it's already available in the scope, why not use it?
This feels like a reusable component but it's not. Let's improve it!
Without this patch the user can only mint a Hypercert with their
connected browser wallet.

By passing the Safe address into the SDK function the Safe flow is
invoked. The minting dialog now shows fewer steps and proposes a Safe
transaction on successful signature.
Copy link

vercel bot commented Mar 11, 2025

@pheuberger is attempting to deploy a commit to the Hypercerts Foundation Team on Vercel.

A member of the Team first needs to authorize it.

@pheuberger pheuberger closed this Mar 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants